Currently, the workflow requires token transfer messages all relayed from Asset Hub(AH), so from the perspective of the ORML chain there is not much difference from the integration flow with any other sibling chain(e.g. mainly to register foreign token and it's XCM Location in asset-registry module which the 3rd team should already be familiar with).

Previously I planned to add the template chain into our e2e setup and write smoke tests for it, but consider above seems not worthwhile for that. The emulated test and the companion PR with changes required should be pretty enough for demonstration. Meanwhile we may not want to keep maintaining the orml codes always to recent release.

So I prefer not to merge this PR and just leave it here as a reference for the integration flow.

Sounds good Ron, I agree that we should not merge this since the Snowfork/parachain-orml-template repo should be sufficient.

Leave Snowfork/parachain-orml-template#1 and close this one.